What Are Messages For?
When information arrives from the outside world at a bus stop it is translated into the B2MML standard and sent onto the Bus as a message.
Each message contains information and specifies an action that needs to be carried out using that information.
Message Names
The name of each message contains the action that will be carried out and the type of information that the message contains. There are five different actions that can be performed:Get, Process, Change, Cancel and Acknowledge.
And three different types of information:
Operations capability: What is available?
Operations schedule: What needs to be done?
Operations performance: What has been done?
By combining these we get messages types such as ProcessOperationsSchedule, ChangeOperationsSchedule and ProcessOperationsPerformance.
Which Messages Can Bus Stops Publish/Subscribe To?
These are all the messages that the bus stops can publish and subscribe to.
|
OT Bus Stop |
IT Bus Stop |
ADOS |
Archive |
||||
|
Publish |
Subscribe |
Publish |
Subscribe |
Publish |
Subscribe |
Subscribe |
|
| ProcessOperationsPerformance |
|
|
|
|
|
|
|
| ProcessOperationsSchedule |
|
|
|
|
|
|
|
| GetOperationsSchedule |
|
|
|
|
|
||
| CancelOperationsSchdedule |
|
|
|
|
|
|
|
| ProcessOperationsCapability |
|
|
|
|
|
|
|
| ProcessWorkPerformance |
|
|
|
|
|
|
|
| AcknowledgeOperationsSchedule |
|
|
|
|
|
|
|
| ChangeOperationsSchedule |
|
|
|
|
|
|
|
Message Descriptions
The names of the messages describe what they do. The following list gives extra information where required:
ProcessOperationsPerformance
The OT bus stop sends a ProcessOperationsPerformance message under the following conditions:
Message sent with response state set to Ready when a work order has been dispatched.
Message sent with response state set to Running when a work order is updated by the UpdateBatch action where the CloseOrder has been set to false.
Message sent with response state set to Completed when a work order is updated by the UpdateBatch action where the CloseOrder has been set to true.
This message can also be used to transfer files from production line to an IT system.
ProcessOperationsSchedule
Can be used to transfer files from IT systems to the production line.
GetOperationsSchedule
The GetOperationsSchedule message is sent from the OT bus stop to the IT bus stop to request an operations schedule for a specified operation. The IT bus stop will respond with a ShowOperationsSchedule message which is downloaded using the DownloadOrderOperation action. Normally an EnqueueOrderOperation is used.
CancelOperationsSchedule
The OT bus stop processes a CancelOperationsSchedule message automatically without any actions assigned to it. The OT bus stop only needs to subscribe to these messages.
CancelOperationsSchedule messages will only affect existing, non-running work orders. These messages are ignored for running work orders.
ProcessOperationsCapability
This message is published onto the Bus from an OT bus stop by the PublishAsOperationsCapability action.
ProcessWorkPerformance
OT Bus Stop: The message is published to the bus by the PublishAsWorkPerformance action. The UpdateBatch and DownloadToChannelMessage bus message actions will convert the message to a shopfloor message for further processing.
IT Bus Stop and ADOS Bus Stop: The message is published to the bus by the PublishOnTheBus channel message action. The Export bus message action exports the message to a channel message for further processing.
AcknowledgeOperationsSchedule
The OT bus stop sends an AcknowledgeOperationsSchedule message back to the IT bus stop acknowledging that the work orders contained in a ProcessOperationsSchedule message have been enqueued. This happens if an EnqueueOrderOperation or DownloadOrderOperation action is assigned to a ProcessOperationsSchedule message.
ChangeOperationsSchedule
The OT bus stop processes a ChangeOperationsSchedule message automatically without any actions assigned to it. The OT bus stop only needs to subscribe to these messages.
ChangeOperationsSchedule messages will only affect existing, non-running work orders. These messages are ignored for running work orders.